-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Popover: stabilize __unstableShift prop to shift #43845
Conversation
Size Change: +13 B (0%) Total Size: 1.25 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good and tests well 👍 Just left a single question-suggestion.
@@ -221,7 +221,7 @@ function ButtonEdit( props ) { | |||
anchorRef={ ref?.current } | |||
focusOnMount={ isEditingURL ? 'firstElement' : false } | |||
__unstableSlotName={ '__unstable-block-tools-after' } | |||
__unstableShift | |||
shift |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we intentionally keeping the legacy prop here:
__unstableShift |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, just a miss in my find-and-replace 🙈
Done in a8421c5
Dev note
See the dev note in #44195
What?
Closes #43191
Stabilize
__unstableShift
by adding a newshift
prop. The unstable prop is marked and deprecated and will be supported until the release of WordPress 6.3Why?
See #43191
How?
shift
prop__unstableShift
prop, while still supporting the legacy prop.__unstableShift
instances in the repo to useshift
insteadTesting Instructions
trunk
__unstableShift
is not used anymore in the codebase